home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
015a
/
umbdrvr.zip
/
UMB_DRVR.DOC
next >
Wrap
Text File
|
1991-11-12
|
43KB
|
948 lines
UMB_DRVR.DOC Version 5.10 11/12/91 Page 1
UMB_DRVR.SYS Device Driver
UMB provider for DOS 5.0
Copyright (C) 1991, All Rights Reserved
Christopher Blum CompuServe: 76625,1041
1022 East Wayne Avenue INTERNET: 76625.1041@compuserve.com
Wooster, Ohio 44691 BIX: cblum
(216)262-3786
IMPORTANT INFORMATION
UMB_DRVR.SYS carries no warranties expressed or implied. It is
solely up to the user to determine its suitability for use on his/her
machine.
UMB_DRVR.SYS is made available on a 'try before you buy' basis.
It is not crippled in any way, and has no 'advertising'. The latest
version will be available on CompuServe in the IBM forum ( 'GO IBMSYS',
lib 1 ). New versions will be uploaded as more chip sets are supported.
Personal use license ( U.S. funds ) is $25 which should be mailed
to the above address if the program is used after a reasonable trial
period ( 30 days ). Please use the registration form at the end of this
document. Users who register receive the latest version of the program.
Corporate users must contact me for corporate rate or site license
arrangements.
This program is distributed as a self-extracting file containing
the device driver and its associated documentation. Copying and
redistribution is encouraged, but must be the original, unmodified
file containing this documentation, and the transfer must not carry
any fee or charge specific to this program: i.e. general BBS access
or line charges are OK, but no 'download fee' or similar charge. This
means that BBS operators may post this file for download, but may not
charge a specific fee for it, and 'Distribution houses' may charge a
disk-duplication fee, but not a specific charge for the program.
Technical support, including pre-registration questions or install
assistance, is available at your expense at the above telephone number.
Please be aware that I am in the Eastern U.S. time zone ( GMT - 4 or 5
depending on season ) and try to call at a reasonable hour: i.e. 9 AM to
Noon, 1 PM to 5PM, and 7 PM to 10 PM. I can also be contacted via Email
on CompuServe, INTERNET and BIX ( IDs above ) - I monitor my mail almost
every day. You may also leave messages on CompuServe in the IBMSYS forum
section 1. The U.S. Postal Service may also be used, but is not as quick
( address above ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 2
INTRODUCTION
UMB_DRVR.SYS is a DOS 5.0 device driver that will use the shadow
memory capability of the memory controller portion of various chip sets
to:
A) force all roms not specifically excluded to be shadowed, and
B) expand DOS base memory beyond 640KB if possible, and
C) provide UMBs ( Upper Memory Blocks ) to DOS for loading
programs and device drivers into 'high memory'
while NOT using ANY resident memory ( mapped out or otherwise ).
One advantage of this driver is that many if not all other device
drivers and TSR programs may be loaded 'high' including HIMEM.SYS and
EMM386.EXE ( even though the DOS documentation says not! ).
A second advantage of using UMB_DRVR.SYS is that device drivers
that cannot be loaded high when EMM386.EXE is providing UMBs via the
'ram' or 'noems' parameter because of their use of DMA transfers will
sometimes work with UMB_DRVR.SYS: EMM386.EXE remaps ram using virtual-86
mode with the memory management logic on the 386+ chips, and the virtual
address is not the same as the real address for the ram area mapped as
UMBs, whereas UMB_DRVR.SYS uses the hardware external to the cpu and
remains in real mode, allowing DMA transfers within the UMB area. Note
however, that some chip sets do not map the shadow area for DMA access,
so this may not apply.
In addition, remaining in real mode allows programs that must be
able to use protected or virtual-86 mode themselves, such as Borland's
Turbo Debugger ( TD386.EXE / TDH386.SYS ), to operate as intended ( and
yes, TDH386.SYS can be loaded high with no problems ).
With respect to performance of UMB_DRVR.SYS versus EMM386.EXE, here
are some benchmark results supplied by a ( happy ) user:
" System: 386SX 20Mhz, VLSI TOPCAT chip set, 4MB ram, no math processor.
DOS version: MS/DOS 5.0 UMB_DRVR.SYS version: 5.09
Benchmark: CHECKIT 3.0 main system benchmark.
CONFIG.SYS Dhrystones Whetstones
------------------------------------ ---------- ----------
None 3767 76.7K
DEVICE=C:\UMB_DRVR.SYS /C=13 4042 77.1K
DEVICEHIGH=C:\DOS\HIMEM.SYS
DEVICEHIGH=C:\DOS\ANSI.SYS
DEVICE=C:\DOS\HIMEM.SYS 3683 45.7K
DEVICE=C:\DOS\EMM386.SYS NOEMS
DEVICEHIGH=C:\DOS\ANSI.SYS
As you can see, there is a significant difference when using UMB_DRVR,
not to mention the extra memory saved below 640k. The benchmarks ran
faster with UMB_DRVR than they did with no CONFIG.SYS at all. "
UMB_DRVR.DOC Version 5.10 11/12/91 Page 3
INSTALLATION
Installation ( preferably as the first driver ) is via the lines
DEVICE=UMB_DRVR.SYS /C=nn [/M=ssssssssssssssssssssssss]
DOS=[HIGH|LOW],UMB ( *REQUIRED* - turn on DOS 5 UMB support )
in your CONFIG.SYS file. The /C= parameter is required - nn is the chip
set from 'CHIP-SET-SPECIFIC NOTES'. The /M= parameter is optional and is
used to override defaults. It contains characters corresponding to 16K
memory blocks at the following addresses:
/M=ssssssssssssssssssssssss
A0000'||||||||||||||||||||||`FC000---| Only '..' and '--' may be
A4000'||||||||||||||||||||`F8000----| used for the system BIOS.
A8000'||||||||||||||||||`F4000--|
Video AC000'||||||||||||||||`F0000---| '..', '--', '++', and '##'
RAM B0000'||||||||||||||`EC000 | may be used for boot page.
B4000'||||||||||||`E8000 | Use '##' to force area to be
B8000'||||||||||`E4000 | shadowed as part of BIOS.
BC000'||||||||`E0000
|||||||`DC000
||||||`D8000
|||||`D4000
||||`D0000
|||`CC000
||`C8000
|`C4000
`C0000
s = '.' Allow default use of block
'-' Force block to be unused and unshadowed
'+' Force block to be used for UMBs or
to expand DOS base memory beyond 640K
The /M= parameter must always be supplied as all 24 characters, using
the '.' character to fill any positions not forced on or off. For
example, on a VGA system using video memory from A0000 to BFFFF, if
it is in CGA 80 x 25 mode, the only video memory in use is B8000-BFFFF.
In this case, the memory from A0000-AFFFF may be used to expand DOS
base memory beyond 640K ( with some VGA cards ) by using the parameter:
/M=++++....................
Of course, with the system configured like this, if you change the video
mode, undefined ( read as disaster city! ) results will occur.
A second example would be a system where you wish to use EMM386.EXE
to supply EMS memory and wish to use C8000-D7FFF as the EMS base address
range. To accomplish this, use the parameter:
/M=..........----..........
to reserve this memory for EMM386.EXE to use. You will also need to use
the I= parameter for EMM386.EXE to include C8000-D7FFF for its use.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 4
DRIVER OPERATION
The driver must be installed BEFORE HIMEM.SYS is installed. It is
an XMS 2.0 server providing UMBs to DOS via that standard. The chip
set parameter is processed and the proper routine called to remap the
unused shadow ram to DOS-useable memory. Available memory starting at
A0000 is used to expand DOS base memory beyond 640K, and other available
memory ( i.e. above the video memory ) is used for UMBs ( the areas
DOS uses for DEVICEHIGH or LOADHIGH commands ).
The driver by default will not use any areas used for video memory.
It also forces any roms including the system BIOS ( F8000-FFFFF ) to be
shadowed unless specifically excluded. If the BIOS has a 'boot page'
at F0000-F7FFF that the driver can recognize ( containing system / CMOS
setup code - AMI is one brand that has this ), that area will be mapped
as available ram since it is not needed after boot time.
The driver should be loaded as the first driver if possible. This
allows following drivers and resident programs to be loaded high - even
HIMEM.SYS and EMM386.SYS ( DOS documentation says they can't, but it
works - see note about Windows, however ). It will initialize, supply
UMBs, and go away leaving no resident memory anywhere.
Appropriate status and error messages are issued during processing
and a map of the driver's action is displayed.
SYSTEM SETUP EXAMPLE
One of my systems is a 386SX using the Chips and Technologies NEAT
chip set. It has 4MB of RAM and a Hercules Monochrome Graphics card.
I configure 2MB of EMS memory with a base address of C0000-CFFFF using
the NEAT hardware and their supplied software driver RMS386N.SYS. I load
DOS into the HMA using HIMEM.SYS, and also load Borland's Turbo Debugger
device driver TDH386.SYS for 386 virtual debugging ( TD386 ) and the
ANSI.SYS console driver. My CONFIG.SYS looks like this:
BREAK=ON
FILES=30
BUFFERS=40
STACKS=0,0
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /P
DEVICE=C:\UTILITY\UMB_DRVR.SYS /C=01
DEVICEHIGH=C:\DOS\HIMEM.SYS
DEVICEHIGH=C:\BORLANDC\BIN\TDH386.SYS
DEVICEHIGH=C:\UTILITY\RMS386N.SYS
DEVICEHIGH=C:\DOS\ANSI.SYS
DOS=HIGH,UMB
This gives me 704K base memory for DOS, a maximum executable program
size of almost 690K, and 160K in one UMB at D0000-F7FFF with almost 128K
still free in that upper memory block for a mouse driver, network
driver, TSR, etc. I consider that a pretty good cure for 'RAM cram'!
UMB_DRVR.DOC Version 5.10 11/12/91 Page 5
MISCELLANEOUS NOTES
*************
* Boot page *
*************
If UMB_DRVR.SYS uses the 'boot page' area by default and your
system crashes, you need to use the /M= parameter to force it to be
considered part of the BIOS ( use '##' or '--' ). If no 'boot page' is
recognized, you may still be able to use the /M= parameter ( with '++'
for F0000-F7FFF ) to use the area ( if you are brave enough to try it ).
***************
* EMS drivers *
***************
If you run EMS, it is most efficient in terms of contiguous memory
to have your EMS base address immediately following your video ram and
any adjacent rom ( e.g. C0000-CFFFF for CGA or monochrome, C8000-D7FFF
for VGA ) or at the top of the useable area ( e.g. E8000-F7FFF with a
'boot page', E0000-EFFFF without ).
It is more efficient to use the hardware EMS driver for your chip
set if it supports it ( e.g. C & T NEAT ) or for your EMS memory card if
you have one instead of EMM386.EXE; see Introduction re Virtual-86 mode.
If you use a hardware EMS driver, you must use the /M= parameter to
force UMB_DRVR.SYS to exclude the EMS base area.
If you use EMM386.EXE, you must include the I= parameter to allow
it to use the EMS base area, and you must use the /M= parameter to force
UMB_DRVR.SYS to exclude the EMS base area. The EMS base area must be
above where EMM386.EXE is loaded ( i.e. if you load it high, the base
area must be above the UMB area ). Although you cannot specify a frame=
parameter of E800, using I=E800-F7FF will allow EMM386.EXE to set the
frame there. DO *NOT* USE THE 'RAM' OR 'NOEMS' PARAMETERS! This makes
EMM386 remap to supply UMBs and UMB_DRVR has already done that.
See the notes for Windows concerning 386 enhanced mode.
********************************
* ROMs that cannot be shadowed *
********************************
Some roms cannot be shadowed by normal means because they have some
ram they must use mapped in their address space ( e.g. some RLL, ESDI
and SCSI disk controller roms ) and shadowing is normally done using
protected ram. These roms usually will work when shadowed by this driver
if they are within a protection block also containing UMBs. Try letting
UMB_DRVR.SYS shadow the rom and see if it works.
If you find you have a rom that cannot be shadowed, or for some
reason you do not wish to shadow a rom, you must use the /M= parameter
to exclude it from UMB_DRVR.SYS control. Refer to the chip-set-specific
notes for any special considerations.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 6
MISCELLANEOUS NOTES
***********
* Windows *
***********
Windows 3.0 has been tested as follows:
386 enhanced mode:
Windows will *NOT* run in 386 enhanced mode with UMB_DRVR.SYS in
the system. Use EMM386.EXE to provide UMBs if you want to run this way.
Standard mode:
Windows will run in standard mode with UMB_DRVR.SYS installed and
HIMEM.SYS and an EMS driver ( hardware or EMM386.EXE ) loaded high or
low. Note you must have some extended memory to run standard mode - i.e.
do not have EMM386.EXE remap ALL extended memory to expanded.
Real mode:
Windows runs in real mode with UMB_DRVR.SYS installed, HIMEM.SYS
loaded high, and EMM386.EXE loaded LOW, giving 'large frame EMS'. You
can have EMM386.EXE remap everything to expanded in this configuration.
**************************************************************
* User Program access to Upper Memory with DOS managing UMBs *
**************************************************************
1. Record current status of memory system so you can restore it.
int 21H/ax=5800h - returns al=strategy ( see below )
int 21h/ax=5802h - returns al=UMB link state ( see below )
2. Set up for memory allocation / deallocation.
int 21h/ax=5801h/bh=0/bl=strategy int 21h/ax=5803h/bh=0/bl=UMB status
00h - first fit, low memory 00h = remove UMBs from mem chain
01h - best " " " 01h = add UMBs to mem chain
02h - last " " " ( UMBs must be chained for access )
40h - first fit, high memory
41h - best " " "
42h - last " " "
80h - first fit, try high then low memory
81h - best " " " " " "
82h - last " " " " " "
3. Do normal int 21h/ah=48h, int 21h/ah=49h, int 21h/ah=4Ah as desired.
4. Restore values saved in step 1 above.
The system defaults to first-fit-low with UMBs not chained. If you
chain the UMBs, strategies 00/01/02 affect the entire chain. For example
with the UMBs chained and strategy 00, you will get memory from the UMB
area if the request cannot be satisfied from low memory.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 7
DETERMINING YOUR CHIP SET
If your system documentation or CMOS setup screen does not tell you
what chip set you have, the best way to find out is to open the cover on
your system and look at the motherboard. *MAKE SURE THE SYSTEM IS OFF
AND UNPLUGGED* when you do this. The chip you will be looking for is
a larger one with many ( usually 120+ ) pins. The number that identifies
the key chip in the set is listed in the chip-set-specific notes for
each one supported. If you find a matching number on one of the chips on
your motherboard, use the /C= value shown for that set. If you don't see
a match, refer to the sections 'BAD NEWS' and 'COMING ATTRACTIONS'.
CHIP-SET-SPECIFIC NOTES
***************************************************************
* Chips & Technologies CS8221/CS8281 NEAT, CS8223/CS8283 LEAP *
***************************************************************
/C=01 - Chip ID(s): 82C212, 82C812, 82C241, 82C841
These chip sets allow the 384k of motherboard ram at A0000-FFFFF to
relocate to extended memory at 100000-15FFFF on systems with only 1mb of
ram. If this remapping is enabled when UMB_DRVR.SYS enables this area,
the remapping is removed and the size of your extended memory is reduced
by 384k, i.e. it disappears. A small INT 15H stub is installed in the
BIOS stack area at 2DH:5DH to handle situations where your extended
memory size changes. If you shadow anything in your CMOS setup or you
disable the relocation ( see your CMOS setup ), then this stub is not
required and not installed. Note that this applies only to systems with
*EXACTLY* 1MB of memory.
These chip sets map in 16k segments, but write protection for the
area C0000-FFFFF is in 64k segments. To allow maximum memory utilization
the driver marks any segment containing UMBs as read/write. If the 64k
segment also contains a rom shadow, it is not protected.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude any non-rom areas within the 64k segment
( e.g. for a VGA rom at C0000-C7FFF, exclude C8000-CFFFF ).
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.SYS will recognize the EMS setup for these chip sets and
will by default exclude the EMS base segment if the EMS hardware is
enabled. Use of the /M= parameter is not required in this case.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 8
CHIP-SET-SPECIFIC NOTES
****************************
* VLSI Technology VL82C200 *
****************************
/C=02 - Chip ID(s): VL82C201, VL82C202, VL82C203, VL82C204
( all 4 chips required )
This chip set uses a jumper or switch to enable shadow ram ability.
This does not actually cause shadowing, but must be in proper position
for UMB_DRVR.SYS to work. Check your system documentation.
This chip set maps and protects in 64k segments. To allow maximum
memory utilization, 64k segments containing UMBs are set to read/write.
If the 64k segment also contains a rom shadow, it is not protected.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude any non-rom areas within the 64k segment
( e.g. for a VGA rom at C0000-C7FFF, exclude C8000-CFFFF ).
If you must force a rom to be unshadowed, exclude the entire 64k
segment on a 64k boundary ( e.g. for a disk rom at C8000-CBFFF, exclude
C0000-CFFFF ).
*******************
* FOREX FRX36C300 *
*******************
/C=03 - Chip ID(s): FRX36C300
This chip set maps in 32k segments from C0000 to EFFFF, and one 64k
segment for the system BIOS ( F0000-FFFFF ). Ram at A0000-BFFFF is
always remapped to the highest area and cannot be used by the driver.
Protection is set globally, meaning that all used ram ( shadow or UMBs )
is marked read/write.
The chip set also remaps D0000-EFFFF to the highest area if there
is nothing shadowed in that area. When UMB_DRVR.SYS enables this area,
the remapping is removed and the size of your extended memory is reduced
by 128k. A small INT 15H stub is installed in the BIOS stack area at
2DH:5DH to handle situations where your extended memory size changes. If
you shadow something in the area D0000-EFFFF in your CMOS setup ( even
though you may have no rom there ), then this stub is not required and
not installed.
If you must force a rom to be unshadowed, exclude the entire 32k
segment on a 32k boundary ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CFFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 9
CHIP-SET-SPECIFIC NOTES
************************************************************
* Chips & Technologies CS8230 386/AT, CS8231 386/AT Cache, *
* CS8233 PEAK 386/AT, CS82310 PEAK/DM *
************************************************************
/C=04 - Chip ID(s): 82C302, 82C307, 82C311, 82C351
These chip sets maps in 16k segments, but write protection for the
area C0000-FFFFF is in 64k segments. To allow maximum memory utilization
the driver marks any segment containing UMBs as read/write. If the 64k
segment also contains a rom shadow, it is not protected.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude any non-rom areas within the 64k segment
( e.g. for a VGA rom at C0000-C7FFF, exclude C8000-CFFFF ).
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
****************************************************************
* Chips & Technologies 82C235/82C836 SCAT, CB8291/CB8295 ELEAT *
****************************************************************
/C=05 - Chip ID(s): 82C235, 82C836
These chip sets allow the 384k of motherboard ram at A0000-FFFFF to
relocate to extended memory at 100000-15FFFF on systems with only 1mb of
ram. If this remapping is enabled when UMB_DRVR.SYS enables this area,
the remapping is removed and the size of your extended memory is reduced
by 384k, i.e. it disappears. A small INT 15H stub is installed in the
BIOS stack area at 2DH:5DH to handle situations where your extended
memory size changes. If you shadow anything in your CMOS setup or you
disable the relocation ( see your CMOS setup ), then this stub is not
required and not installed. Note that this applies only to systems with
*EXACTLY* 1MB of memory.
These chip sets map in 16k segments, but write protection for the
area C0000-FFFFF is in 32k segments. To allow maximum memory utilization
the driver marks any segment containing UMBs as read/write. If the 32k
segment also contains a rom shadow, it is not protected.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude any non-rom areas within the 32k segment
( e.g. for a rom at C8000-CBFFF, exclude CC000-CFFFF ).
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 10
CHIP-SET-SPECIFIC NOTES
************************
* ETEQ Micro COUGAR II *
************************
/C=06 - Chip ID(s): 82C491 ( same ID but different chips for 386/486 )
This chip set maps in 16k segments from C0000 to EFFFF, and one 64k
segment for the system BIOS ( F0000-FFFFF ). Memory protection is done
in 64k segments from C0000 to EFFFF. The hardware does not allow read /
write access to the area F0000-FFFFF - i.e. the rom can be shadowed and
protected, but the driver cannot use the boot page. The driver also
cannot use the ram at A0000-BFFFF.
The chip set can remap A0000-BFFFF and D0000-EFFFF to the highest
area if no shadowing is done in that area. If this remapping is enabled
and UMB_DRVR.SYS enables the area D0000-EFFFF, the remapping is removed
and the size of your extended memory is reduced by 256k. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow something in the
area D0000-EFFFF in your CMOS setup ( even though you may have no rom
there ) or you disable the remapping, then this stub is not required and
not installed.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude non-rom areas within the 64k segment:
e.g. for a rom at C8000-CBFFF, exclude C0000-C7FFF and CC000-CFFFF. If
you have a VGA rom at C0000-C7FFF, you only need exclude CC000-CFFFF.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 11
CHIP-SET-SPECIFIC NOTES
***************************
* OPTi Sx/AT, Sx/AT Cache *
***************************
/C=07 - Chip ID(s): 82C281, 82C283
These chip sets maps in 16k segments from C0000 to EFFFF, and one
64k segment for the system BIOS ( F0000-FFFFF ). Memory protection is
in 64k segments from C0000 to EFFFF. The hardware does not allow read /
write access to the area F0000-FFFFF - i.e. the rom can be shadowed and
protected, but the driver cannot use the boot page. The driver also
cannot use the ram at A0000-BFFFF.
These chip sets can remap A0000-BFFFF and D0000-EFFFF to the high
end of extended memory if no shadowing is done in either area. If this
remapping is enabled and UMB_DRVR.SYS enables the area D0000-EFFFF, the
remapping is removed and the size of your extended memory is reduced by
256k. A small INT 15H stub is installed in the BIOS stack area at
2DH:5DH to handle situations where your extended memory size changes. If
you shadow something in the area D0000-EFFFF in your CMOS setup ( even
though you may have no rom there ) or you disable the remapping, then
this stub is not required and not installed.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude non-rom areas within the 64k segment:
e.g. for a rom at C8000-CBFFF, exclude C0000-C7FFF and CC000-CFFFF. If
you have a VGA rom at C0000-C7FFF, you only need exclude CC000-CFFFF.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 12
CHIP-SET-SPECIFIC NOTES
********************
* OPTi DX/BB PC/AT *
********************
/C=08 - Chip ID(s): 82C496
This chip set maps in 16k segments from C0000 to EFFFF, and one 64k
segment for the system BIOS ( F0000-FFFFF ). Memory protection is done
in 64k segments from C0000 to EFFFF. The hardware does not allow read /
write access to the area F0000-FFFFF - i.e. the rom can be shadowed and
protected, but the driver cannot use the boot page. The driver also
cannot use the ram at A0000-BFFFF.
The chip set can remap A0000-BFFFF and D0000-EFFFF to the highest
area if no shadowing is done in that area. If this remapping is enabled
and UMB_DRVR.SYS enables the area D0000-EFFFF, the remapping is removed
and the size of your extended memory is reduced by 256k. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow something in the
area D0000-EFFFF in your CMOS setup ( even though you may have no rom
there ) or you disable the remapping, then this stub is not required and
not installed.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude non-rom areas within the 64k segment:
e.g. for a rom at C8000-CBFFF, exclude C0000-C7FFF and CC000-CFFFF. If
you have a VGA rom at C0000-C7FFF, you only need exclude CC000-CFFFF.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
***********************************
* OPTi 386WB PC/AT, 486SXWB PC/AT *
***********************************
/C=09 - Chip ID(s): 82C391, 82C493
These chip sets maps in 16k segments from C0000 to EFFFF, and one
64k segment for the system BIOS ( F0000-FFFFF ). Memory protection is
done in 64k segments from C0000 to EFFFF. The hardware does not allow
read / write access to ram at F0000-FFFFF - i.e. the rom can be shadowed
and protected, but the driver cannot use the boot page. The driver also
cannot use the ram at A0000-BFFFF.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude non-rom areas within the 64k segment:
e.g. for a rom at C8000-CBFFF, exclude C0000-C7FFF and CC000-CFFFF. If
you have a VGA rom at C0000-C7FFF, you only need exclude CC000-CFFFF.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 13
CHIP-SET-SPECIFIC NOTES
***********************
* OPTi 386/486WB EISA *
***********************
/C=10 - Chip ID(s): 82C682
This chip set maps and protects in 16k segments at C0000-DFFFF, one
64k segment at E0000 and one 64k segment for the system BIOS at F0000.
The 'boot page' area can be used if recognized or forced, but the driver
cannot use the ram at A0000-BFFFF.
If one of the 64k segments contains both shadowed rom and UMB area,
it is marked read/write. All shadowed roms in the C0000-DFFFF area are
write-protected.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ) unless it is in the E0000 block or you wish to force the
BIOS ( F0000-FFFFF) to be unshadowed. Then you must exclude the entire
64k block ( E0000-EFFFF and/or F0000-FFFFF ).
****************************************
* Elite Microelectronics Eagle, Falcon *
****************************************
/C=11 - Chip ID(s): e88C311, e88C411
These chip sets map and protect in 16k segments for the entire area
C0000-FFFFF. All shadowed roms are write-protected. UMB_DRVR cannot use
the ram at A0000-BFFFF.
These sets always remap A0000-BFFFF to the highest memory area, and
can selectively remap C0000-FFFFF in 64k blocks if no shadowing is done
within the 64k block. If this remapping is active and UMB_DRVR enables
shadow memory within one of the remapped 64k blocks, the remapping is
removed and the size of your extended memory is reduced. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow something in each
64k area from C0000 to FFFFF in your CMOS setup ( even though you may
have no rom there ) or you disable the remapping, then this stub is not
required and not installed.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 14
CHIP-SET-SPECIFIC NOTES
*************************
* VLSI Technology SCAMP *
*************************
/C=12 - Chip ID(s): VL82C310, VL82C311, VL82C311L
These chip sets map and protect in 32k segments for A0000-BFFFF,
16k segments for C0000-DFFFF, and 32k segments for E0000-FFFFF. If a
rom shadow shares a 32k segment from E0000 to FFFFF with a UMB area, it
is marked read/write. Any shadowed rom from C0000-DFFFF is protected, as
is any 32k segment from E0000 to FFFFF that is all shadowed rom.
These sets can remap A0000-FFFFF to the highest memory area if no
shadowing is done and system memory is 1MB, 2MB, 3MB or 4MB. If remap
is active and UMB_DRVR enables any shadow memory, the remapping is
removed and the size of your extended memory is reduced. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow anything in your
CMOS setup or you disable the remapping, then this stub is not required
and not installed. Note that this applies only to systems with *EXACTLY*
1MB, 2MB, 3MB or 4MB installed.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies if it is between C0000 and DFFFF ( e.g. for a
disk rom at C8000-CBFFF, exclude C8000-CBFFF ). If it is between E0000
and FFFFF, exclude all areas in the 32k segment ( e.g. for a disk rom at
E0000-E3FFF, exclude E0000-E7FFF ).
*********************************************
* VLSI Technology VL82C286, VL82C386 TOPCAT * ( These sets are all made
* Intel 82340SX, 82340DX * by VLSI Technology )
*********************************************
/C=13 - Chip ID(s): ( VLSI ) VL82C320, VL82C320A, VL82C330
( Intel ) 82343, 82343A, 82346
These chip sets map and protect in 16k segments for the entire area
from C0000 to FFFFF. All shadowed rom areas are protected. The video
area ( A0000-BFFFF ) and the boot page area ( F0000-F7FFF ) can only be
utilized on the VL82C320 / 82343 'A' revision chips. UMB_DRVR recognizes
the various chips and forces restrictions accordingly.
These sets can remap A0000-FFFFF to the high end of extended memory
if no shadowing is done and system memory is exactly 1MB or 2MB. If this
remapping is active and UMB_DRVR enables shadow memory, the remapping is
removed and the size of your extended memory is reduced. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow anything in your
CMOS setup or you disable the remapping, then this stub is not required
and not installed. Note that this applies only if the system memory size
is *EXACTLY* 1MB or 2MB.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 15
CHIP-SET-SPECIFIC NOTES
*******************************
* OPTi HiD/386 AT, HiB/486 AT *
*******************************
/C=14 - Chip ID(s): 82C382, 82C482
These chip sets map in 16k segments from C0000 to EFFFF and one 64k
segment for the system BIOS ( F0000-FFFFF ). Memory protection is done
in 64k segments from C0000 to EFFFF. The hardware does not allow read /
write access to the area F0000-FFFFF - i.e. the rom can be shadowed and
protected, but the driver cannot use the boot page. The driver also
cannot use the ram at A0000-BFFFF.
The chip sets can remap A0000-BFFFF and D0000-EFFFF to the highest
area if no shadowing is done in that area. If this remapping is enabled
and UMB_DRVR.SYS enables the area D0000-EFFFF, the remapping is removed
and the size of your extended memory is reduced by 256k. A small INT 15H
stub is installed in the BIOS stack area at 2DH:5DH to handle situations
where your extended memory size changes. If you shadow something in the
area D0000-EFFFF in your CMOS setup ( even though you may have no rom
there ) or you disable the remapping, then this stub is not required and
not installed.
Although it should not be necessary, if you wish to have a rom be
shadowed and protected, exclude non-rom areas within the 64k segment:
e.g. for a rom at C8000-CBFFF, exclude C0000-C7FFF and CC000-CFFFF. If
you have a VGA rom at C0000-C7FFF, you only need exclude CC000-CFFFF.
If you must force a rom to be unshadowed, you need only exclude the
16k segment(s) it occupies ( e.g. for a disk rom at C8000-CBFFF, exclude
C8000-CBFFF ).
UMB_DRVR.DOC Version 5.10 11/12/91 Page 16
ERROR MESSAGES
***************************
* Shadow ram test failure *
***************************
This message is issued when the shadow ram read/write test fails.
It is usually an indication that you do not have your system configured
properly for UMB_DRVR.SYS, you are forcing use of unavailable memory, or
you do not have the chip set you have specified. Check your CMOS setup
and any jumpers or switches per your system documentation. Also review
the chip-set-specific notes earlier in this document for requirements.
This can also occur if you are trying the example listed earlier
about using a portion of the video ram on a VGA system in CGA mode and
your VGA hardware will not allow it.
******************************
* Chip not found / bad setup *
******************************
As much as possible, UMB_DRVR.SYS tries to verify that you have the
chip you indicated in the /C= parameter and that it is set up properly.
Refer to the chip-set-specific notes and correct your CMOS system setup.
If you are sure you have the chip set, have specified it correctly,
and have it set up properly, contact me ( see initial section of this
documentation ) and I will try to straighten things out.
*************************
* XMS already installed *
*************************
You have not installed UMB_DRVR.SYS before HIMEM.SYS, or you have
omitted or incorrectly specified the 'DOS=xxxx,UMB' line in your
setup. Correct your CONFIG.SYS file and and reboot.
*************************
* Incorrect DOS version *
*************************
UMB_DRVR.SYS requires DOS 5.0 for proper operation.
************************
* Invalid parameter(s) *
************************
On the DEVICE= statement for UMB_DRVR.SYS you have either:
A) omitted or incorrectly specified the /C= parameter, or
B) specified the /M= parameter incorrectly.
Check that you have entered the proper 2-digit number for your chip set
and that ( if specified ) the /M= parameter contains 24 valid characters
from the set '.' ( period ), '-' ( minus ), '+' ( plus ) and '#' ( pound
sign ). Correct the DEVICE= statement in CONFIG.SYS and reboot.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 17
*************************************************
* BAD NEWS ( CHIPS THAT WILL NOT BE SUPPORTED ) *
*************************************************
Intel:
82335, 82335SX - Lock feature prohibits access
Sun Electronics:
SUNTAC ST62BC002 - No shadow ram support
VLSI Technology:
VL82C10x series - No shadow ram support
Western Digital:
FE3021, FE3021A ( Faraday ) - Lock feature prohibits access
****************************************************
* COMING ATTRACTIONS ( SUPPORT UNDER DEVELOPMENT ) *
****************************************************
Headland Technology:
HT series[*] ( 286/386SX )
Intel:
82359 ( EISA 386DX/486 )
OPTi:
L1/L2 Notebook ( 386DX/486 cache )
Silicon Integrated Systems ( SIS ):
85C310, 85C401 ( 386DX/486 cache )
Sun Electronics:
SUNTAC ST62C241, ST62C251 ( 286/386SX )
Texas Instruments:
TACT83442 ( 386SX/386DX/486 )
VLSI Technology:
VL82C486 ( 486 )
Western Digital:
WD6000[*] ( Micro Channel 386SX/386DX/486 )
WD75C10[*], WD76C10[*], WD76C10L[*] ( 286/386SX )
WD7710[*], WD7910[*] ( 386SX )
[*] - Support questionable, may be minimal ( only 64K of UMBs ).
If your chip set is not listed, I will try to add it if you can get
me the documentation or put me in touch with the chip set manufacturer.
UMB_DRVR.DOC Version 5.10 11/12/91 Page 18
********************
* REVISION HISTORY *
********************
5.10 [11/12/91] - Added Chips & Technologies PEAK/DM,
OPTi Sx/AT Cache, HiD/386 AT, HiB/486 AT;
Fixes for VLSI Technology TOPCAT / Intel 82340,
special conditions remapping extended memory
on Chips & Technologies NEAT, LEAP and SCAT,
miscellaneous logic improvements;
Documentation updated and reorganized
5.09 [10/25/91] - Fix for VLSI Technology TOPCAT / Intel 82340
5.08 [10/14/91] - Fix for boot page special condition
5.07 [10/13/91] - Added VLSI Technology SCAMP, TOPCAT / Intel 82340
5.06 [10/12/91] - Added Elite Microelectronics Eagle, Falcon
5.05 [10/09/91] - Added OPTi Sx/AT, DX/BB PC/AT, 386WB PC/AT,
486SXWB PC/AT, 386/486WB EISA
5.04 [10/02/91] - Added ETEQ Micro COUGAR II
5.03 [09/21/91] - Added Chips & Technologies 386/AT,
386/AT Cache, PEAK, SCAT, ELEAT;
Removed setup requirements
5.02 [09/12/91] - Added FOREX FRX32C300;
Added support for use of 'boot page' area;
Fix for VLSI Technology VL82C200;
Default all roms shadowed
5.01 [09/04/91] - Added VLSI Technology VL82C200
5.00 [09/01/91] - Support for Chips & Technologies NEAT, LEAP;
Original release version
***** END OF DOCUMENTATION *****
UMB_DRVR.SYS, Version 5.10 [ 11/12/91 ] Registration Form
***** Please Type or Print Clearly *****
Name:____________________________________________________
Address:_________________________________________________
_________________________________________________
City/State_______________________________________________
Zip/Postal Code__________________________________________
***** Telephone number_________________________________________
* *
* * Email system / routing / ID______________________________
* *
* * ____________________________________________________
* *
* O * Computer description, configuration, chip set, etc.
* *
* P * ____________________________________________________
* *
* T * ____________________________________________________
* *
* I * ____________________________________________________
* *
* O * Comments_________________________________________________
* *
* N * ____________________________________________________
* *
* A * ____________________________________________________
* *
* L * ____________________________________________________
* *
* * ____________________________________________________
* *
* * ____________________________________________________
* *
***** ____________________________________________________
Cost ( U.S.Funds ): $25
Mail to: Christopher Blum
1022 East Wayne Avenue
Wooster, Ohio 44691